Skip to content

Conversation

@mohammad-ahmadi1
Copy link

@mohammad-ahmadi1 mohammad-ahmadi1 commented Oct 14, 2025

I still have this issue 17004 in the latest deployment. This is a quick fix to it already tested locally.
In the recent version of mariadb the argument changed and should follow as committed.

@snipe
Copy link
Member

snipe commented Oct 20, 2025

Hi there - thanks for this! Can you please re-target this PR to point to the develop branch, per our Contributing documentation?

You don't need to close and re-open. After you create a pull request, you can modify the base branch so that the changes in the pull request are compared against a different branch. By changing the base branch of your original pull request rather than opening a new one with the correct base branch, you’ll be able to keep valuable work and discussion.

mhuxq

Thanks!

@mohammad-ahmadi1 mohammad-ahmadi1 changed the base branch from master to develop October 21, 2025 16:54
@mohammad-ahmadi1
Copy link
Author

mohammad-ahmadi1 commented Oct 21, 2025

Hi @snipe thanks for letting me know. I changed the base branch.

Copy link
Member

@uberbrady uberbrady left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me - the db-dumper package does have a setSkipSsl() method you can call on it, but I don't see anywhere that the laravel-backup package actually calls that. So this is probably the best way to go.

@snipe snipe merged commit 07256fd into grokability:develop Oct 28, 2025
10 checks passed
@snipe
Copy link
Member

snipe commented Oct 30, 2025

This seems to be causing issues for some users :( #18118

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants